Files that won't Load!

his is quite an uncommon occurence on the Macintosh and usually one on three things.

  1. The computer says that the application "unknown" has unexpectedly quit due to an error type 1.
    This is the most common error and it is usually a one-off error, try again a few times, and if that fails, restart and then try. If this still fails another problem could be the files preferences. Try dragging them out of your preferences folder. You will have to re-configure the application and possibly put a serial code back into it, but if this works, delete the old preferences and everything should be fine. If not, put the old preferences back into the preferences folder (overwriting the newer one that may just have been created), there is a more serious problem.

  2. The computer says that the application "unknown" has unexpectedly quit due to an error type 1. (Again)
    This error can also happen if an application suddenly finds something has been using its memory, which can occur from time to time. The best way round this problem can be found under the Extended Questioning section in the Crashes section. If this fails, it is best unfortunately, to assume the application has been corrupted somehow and you should re-install it from the master disks/CD.

  3. The computer says that the application "unknown" has unexpectedly quit due to an error type -30 to -40, 25 or 33
    These errors are mainly due to a lack of memory regardless of what the errors actually mean. They are more common if you are using large amounts of colours on the screen at once, resulting in larger than normal memory requirements. Another reason may be the use of Virtual Memory and/or RAM Doubler if you have it installed. They very rarely mean a duff application, but usually one that has become memory starved.

Some applications are very picky about what memory settings they require. Before writing off an application as duff it is a good idea (especially for older ones) to try launching without Virtual Memory / 32 bit addressing / Modern Memory Manager on especially for the oldest ones. These settings can be toggled using the Memory control panel. If one or more of the options does not exist, don't worry, it may not be applicable to your computer.

Other Problems

This is an interesting little error which has a very informative box

hat has actually happened is that something, somewhere (or someone) has told the computer that "Simple Text" is not actually a program but an alias. What's an alias? The computer is fortunately smart enough to realise that this is not the case and has reset it back again for you. Re-loading will now result in a proper launch. This error is usually a result of an error in the directory of the computer and it is worth rebuilding the desktop if it occurs just in case. Click here if you want more info on this.

or anyone vaguely interested, this little error can be created by anyone who has a copy of Snitch, ResEdit or any other programs that allows you to change Finder Flags. For ResEdit users, simply open the application, get info on it and make sure the Alias flag is checked and the INITED flag is not. Save out and the program should now have italic writing like any other alias. Double clicking will result in the above error and the Finder will put the correct flags back automatically. Don't worry, you can't damage the application this way. Though it is still a good idea to make a backup copy first.

Floating Point Co-processer not installed!

This error is totally unpredictable and is almost never the real reason for a force quit or crash. I have seen this error several times on a IIci with an FPU. It is far more likely to be the result of an error type 4 (Divide by 0 error) or a "one-off" error due to a problem with the memory being used by the application at the time. It goes to show again that error types are usually completely irrational as the error can get processed as if it did not exist for a long time before an application suddenly realises that it has one. The error number that comes up is nearly always due to a problem the error causes quite a while after it started.

he chance of this error actually occurring is minimal. The error probably had absolutely nothing to do with the FPU. Very few programs actually require an FPU at all. Most never use them anyway, but a small number will take advantage of them if they are present, though they do not complain if they are not. e.g. Microsoft EXCEL.

If you really want to check that your FPU is seated correctly go ahead and do so. However, do go and get a specialist to do so (where specialist is someone Apple authorised), because the insides of the CPU is where 'the sun don't shine'. If you take a look for yourself, you invalidate your Warranty. Do as you think right.

Back to: Crashes, Main Trouble menu.